E-mail synchronization between heterogeneous mail servers

ABSTRACT

A method or system for synchronizing e-mail messages for a user, particularly for POP3 protocols. E-mail messages addressed to the user are received at an e-mail control at a local server, from an external e-mail server. The e-mail control stores each e-mail message in a consolidated e-mail storage at the local server. The e-mail control stores a message identifier for each e-mail message, in a message identifier storage at the local server. It is determined whether an e-mail message in the consolidated e-mail storage has been deleted from the external e-mail server, and if so, then the e-mail message is deleted from the consolidated e-mail storage.

BACKGROUND OF THE INVENTION

1. Field of the invention

The present invention relates to the storage and retrieval of e-mailmessages. More particularly, it relates to synchronizing e-mail messagesfor the same user amongst multiple mailboxes, on heterogeneous servers.

2. Description of the related art

An e-mail user may have more than one e-mail account on different mailservers. Mail for the user may be forwarded to one of the servers, ormail may be consolidated at one server.

This creates duplicate e-mail messages on the different servers. Each ofthe duplicate messages then must be separately read and deleted,unfortunately requiring additional time and attention from the user.

This problem is particularly acute for mail servers where there is noconventional technology enabling synchronization between two or moresuch mail servers. An example of this is POP3 mail servers. Mostcommercial external e-mail servers offer only the POP3 protocol fore-mail retrieval, thus making the problem both more universal and moresevere.

The IMAP4 protocol was built to solve the mailbox synchronizationproblem, however, it is not available on most interne email servers.

Various formats for e-mail messages have been prescribed. Onewidely-used standardized format for e-mail message is encouraged by RFC822, expressly incorporated herein by reference. These standards use,among other things, a message identifier which is intended to be uniqueto an e-mail. These standards do not, however, provide a way tosynchronize or consolidate e-mail.

BRIEF SUMMARY OF THE INVENTION

According to the invention, there is provided a method or system forsynchronizing e-mail messages for a user. E-mail messages addressed tothe user are received at an e-mail control at a local server, from anexternal e-mail server. The e-mail control stores each e-mail message ina consolidated e-mail storage at the local server. The e-mail controlstores a message identifier for each e-mail message, in a messageidentifier storage at the local server. It is determined whether ane-mail message in the consolidated e-mail storage has been deleted fromthe external e-mail server, and if so, then the e-mail message isdeleted from the consolidated e-mail storage.

Optionally, the invention includes multiple external e-mail servers. Afurther option is, responsive to a user command, providing e-mailmessages from the consolidated e-mail storage, to the user. In anotheralternative, the system is used by multiple users, and the consolidatede-mail storage includes storage for e-mail associated with other users.Optionally, the step of determining includes comparing messageidentifiers in the message identifier storage to message identifiers ine-mail received from the external e-mail server. Alternatively, the stepof determining includes comparing the message identifiers of e-mail onthe external e-mail server to the message identifiers in the messageidentifier storage, or, comparing the message identifiers in the messageidentifier storage to the message identifiers of e-mail in theconsolidated e-mail storage

According to a further option, the local server connects to the externale-mail server, as the user. E-mail messages for the user are requestedfrom the external e-mail server.

These and other objects, features and advantages of the presentinvention are readily apparent from the following drawings and detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating forward synchronization of e-mailmessages, according to the invention;

FIG. 2 is a block diagram illustrating reverse synchronization;

FIG. 3 is a flow chart illustrating the preferred embodiment of forwardsynchronization;

FIG. 4 is a flow chart illustrating the preferred embodiment of reversesynchronization; and

FIG. 5 is a block diagram illustrating use of the invention withmultiple mail accounts on multiple mail servers.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Reference is made to FIG. 1, illustrating a simple example of forwardsynchronization of e-mail messages. An e-mail system includes server A101, server B 103, stored e-mail 105, e-mail control 107, consolidatede-mail 109, and synchronized message identification numbers (messagei.d.) 111.

In this simple example, Server A 101 has stored e-mail 105 for aparticular user, and thus functions as the user's primary (and only, inthis example) mail server. It is possible, as discussed below inconnection with FIG. 5, for a particular user to have multiple e-mailaccounts on several servers. Server A could be any computer systemconfigured for e-mail storage and/or retrieval. Numerous conventionalsystems are appropriate.

Server B 103 includes e-mail control 107, consolidated e-mail 109, andsynchronized message i.d.'s 111. Server B functions as the consolidatingmail server, which a user may use to see a combination of all of theuser's messages.

E-mail control 107 provides synchronization control of e-mail from theuser's external e-mail servers. This is described in detail below.

The consolidated e-mail 109 is advantageously a storage of e-mail,reflecting the last-updated combined e-mail for the user. (The e-mailcontrol may be used by multiple e-mail users, and thus the consolidatede-mail may be used by multiple different users under various knowntechniques for sharing storage space.) The consolidated e-mail should bestored in order to reflect accurately all of the last updated e-mail,including contents thereof. Preferably, the consolidated e-mail 109 arelocated on or are rapidly accessible by the server B 103.

Preferably, the system includes the synchronized message i.d.'s 111. Itis advantageously a stored list of message i.d.'s. Each conventionale-mail is provided with a unique message i.d., to identify identicale-mail messages. Each of the synchronized message i.d.'s correspond toone of the combined e-mail messages in the consolidated e-mail 109. Itis advantageous to utilize the list of message i.d.'s in order torapidly determine the contents of the consolidated e-mail; althoughoptional, this is preferred.

On a periodic basis, forward synchronization is performed as follows.The e-mail control 107 connects 1 to each of the mail servers (in thisexample, Server A 101) and requests e-mail messages 2 stored on Server Afor a user. Server A sends e-mail messages 3 . . . n to Server B.Preferably, the e-mail and the message i.d. of each e-mail is stored inthe consolidated e-mail 109 (steps 4, 5). The message i.d.s of e-mail onServer A 101 are compared to message i.d.s stored in the consolidatede-mail 109. If a message i.d. for an e-mail in the consolidated e-mail109 (that originated from Server A) no longer has a counterpart onServer A 101, the message and the message i.d., is removed from Server B(step 6).

FIG. 2 illustrates a simple example of reverse synchronization, whichcan be used in conjunction with, or independently from, forwardsynchronization. Forward synchronization is used when the e-mail accounton Server A is the controlling mailbox, and reverse synchronization isused when the e-mail account on Server B is the controlling mailbox. Ifeither side should update the other, then both forward and reversesynchronization can be used together. After performing the connection,as above, all message i.d.'s in the synchronized message i.d.'s database111 are checked against the consolidated e-mail 109. If e-mail no longerexists in the consolidated e-mail, then the e-mail control will removethe message from Server A (for example, by sending a request to deletethe e-mail message).

FIG. 3 is a flow chart illustrating the preferred embodiment of forwardsynchronization.

At step 301, the e-mail control opens a connection to an external mailserver. At step 303, the e-mail control requests an external messagecount of e-mails on the external mail server. At step 305, the e-mailcontrol retrieves the e-mail messages from the external mail server intostorage A (preferably local storage). At step 307, the e-mail controlstores the message i.d.'s for the retrieved e-mail messages in storageA.

At step 309, the e-mail control opens a connection to the consolidationmail server. At step 311, the e-mail control retrieves previously syncedmessages into a storage B. The previously synced messages areadvantageously located in Server B's e-mail store, and are previouslystored there from a previously run consolidation process. At step 313,the next message i.d. is retrieved by the e-mail control from the nexte-mail in storage B. At step 315, the e-mail control checks for any nextmessage i.d. If there is no message i.d., this process ends 323. Ifthere is a next message i.d., and if the next message i.d. is present instorage A (step 317), the e-mail control simply returns to step 313. Ifthere is a next message i.d., and the next message i.d. is not presentin storage A (step 317), the message control deletes the message fromthe consolidation mail server (step 319); deletes the message and themessage i.d. from the storage B message i.d. database , and returns tostep 313.

The following instructions are one example of a POP3 Forward Syncaccording to the invention:

-   1. Open a POP3 connection to external mail server A.-   2. Log in with Username and password.-   3. Request message count.-   4. Retrieve all messages into memory (“collection A”). Collection A    represents all messages on the external mail server.-   5. Scan each retrieved message header for the message i.d., and save    the message i.d. in collection A.-   6. Open an IMAP4 connection to consolidation mail server B.-   7. Login with user name and password.-   8. Open a connection to a local database storage for message i.d.s.-   9. Read into collection B previously synched message ids for this    user. Collection B represents all previously synched messages.-   10. Get first (next) message i.d. from collection B. At the end of    the collection, the process is complete.-   11. Check to see if this message i.d. exists in collection A.-   12. If it does exist, skip it and go back to step 10.-   13. If it does not exist, do a command (e.g., IMAP Delete) to remove    e-mail message from Consolidation mail server B.-   14. Delete this message from collection B and from the message i.d.    database.-   15. Continue with step 10.

FIG. 4 is a flow chart illustrating the preferred embodiment of reversesynchronization. In step 401, the e-mail control opens a connection tothe external mail server. At step 403, the e-mail control requests anexternal e-mail message count. At step 405, the e-mail control retrievesthe external e-mail messages into storage A, and at step 407, the e-mailcontrol stores the message i.d.'s for the retrieved message in storageA.

At step 409, the e-mail control opens a connection to the consolidationmail server. At step 411, previously synched messages are stored intostorage B. At step 413, the e-mail control gets the next message i.d.from the next e-mail in storage B. At step 415, the e-mail controlchecks whether there was a next message i.d. If there was no nextmessage i.d., the process ends (step 425). If there is a next messagei.d. (step 415), and if the message i.d. is not in storage B (step 417),e-mail control returns to step 413. If there was a next message i.d.(step 415), and if the message i.d. exists in storage (step 417) and themessage exists on the consolidation server (step 419), e-mail controlreturns to step 413. If there was a next message i.d. (step 415), and ifthe message i.d. exists in storage b (step 417), and if the message doesnot exist on the consolidation server (step 419), then the e-mailcontrol deletes the message from the external mail server (step 421),deletes the message and message i.d. from storage A and the localmessage i.d. database (step 423), and returns to step 413.

The following is an example of a POP3 Reverse Sync according to theinvention:

-   1. Open a POP3 connection to an external mail server (server A).-   2. Login with user name and password.-   3. Request the message count.-   4. Retrieve all message into a memory collection, collection A.    Collection A will represent all message on the external mail server.-   5. Scan each retrieved message header for the message i.d., and save    the message i.d.s in collection A.-   6. Open an IMAP4 connection to the consolidation mail server (server    B).-   7. Login with user name and password.-   8. Open a connection to local database storage for sync'ed message    ids-   9. Read from the database into collection B, all previously synched    message ids for this user. Collection B then represents all    previously synched message.-   10. Get the first (next) message i.d. from collection A. At the end    of collection A, the process is complete.-   11. Check to see if the message i.d. for the retrieved message    exists in the consolidated mail server, by looking through the    message id collection.-   12. If it does not exist, skip it and go back to step 10.-   13. If it does exist, do a search to see if this message exists in    the email account on the consolidated mail server, server B.-   14. If the message does not exist, delete the message from the    external mail server with an appropriate command, such as POP3    Delete. Delete the message from collection A and remove the message    i.d. from the local message i.d. database.-   15. If the message does exist, skip this message and go back to step    10.

FIG. 5 is a block diagram illustrating multiple e-mail accounts onmultiple servers. A user might have an e-mail account on more than oneserver. In the illustration, the user has an e-mail account on server A101, via a local network connection 501; and servers C . . . X 101 viaan internet connection 503, 505, 507. A user could also have an e-mailaccount on server B 103, the e-mail system including the e-mail control.

When a user has more than one e-mail account, the e-mail control wouldcontact each of the servers on which the user has an e-mail account, inorder to update the consolidated e-mail. The databases would include anidentifier indicating the external e-mail server on which the e-mailoriginated. Conventionally, the Server Name or Domain Name woulduniquely identify each server.

The consolidated e-mail could be updated on a pre-determined periodicschedule, or alternatively as initiated by a user or system operator.

While the preferred mode and best mode for carrying out the inventionhave been described, those familiar with the art to which this inventionrelates will appreciate that various alternative designs and embodimentsfor practicing the invention are possible, and will fall within thescope of the following claims.

1. A method for synchronizing e-mail messages for a user, comprising thesteps of: (A) receiving, at an e-mail control at a local server, aplurality of e-mail messages addressed to the user, from an externale-mail server; (B) storing, by the e-mail control, each e-mail messageof the plurality of e-mail messages, in a consolidated e-mail storage atthe local server; (C) storing, by the e-mail control, a messageidentifier for each e-mail message, in a message identifier storage atthe local server; (D) determining whether an e-mail message in theconsolidated e-mail storage has been deleted from the external e-mailserver, and if so, then deleting the e-mail message from theconsolidated e-mail storage of the local e-mail server. 2-24. (canceled)